-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ES body
removal] @elastic/observability-ui
#204873
Open
afharo
wants to merge
5
commits into
elastic:main
Choose a base branch
from
afharo:esclient/remove-deprecated-body/elastic/observability-ui
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[ES body
removal] @elastic/observability-ui
#204873
afharo
wants to merge
5
commits into
elastic:main
from
afharo:esclient/remove-deprecated-body/elastic/observability-ui
+38
−39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
afharo
added
release_note:skip
Skip the PR/issue when compiling release notes
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
labels
Dec 19, 2024
…-deprecated-body/elastic/observability-ui
…-deprecated-body/elastic/observability-ui
afharo
added
Team:Observability
Team label for Observability Team (for things that are handled across all of observability)
Team:obs-ux-management
Observability Management User Experience Team
labels
Jan 21, 2025
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]Page load bundle
History
cc @afharo |
Pinging @elastic/unified-observability (Team:Observability) |
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
release_note:skip
Skip the PR/issue when compiling release notes
Team:obs-ux-management
Observability Management User Experience Team
Team:Observability
Team label for Observability Team (for things that are handled across all of observability)
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
in preparation for 9.0, we're trying to remove the deprecated
body
param in the ES client.To make it easier to review, the changes have been split into multiple PRs, trying to group them per code owner as much as possible.
However, unfortunately, due to cross-dependencies, your team may be pinged more than once. Apologies for that additional noise.
What changes?
Nothing changes internally. The ES client already places everything where it should be when performing the request to ES (URL vs. query string vs. body params).
The main change is in the usage: when using the JS ES client, developers don't need to identify what goes in the body and what goes in the URL. All settings are provided at the root level. So, in summary, the change is:
For this reason, enabling the "Hide whitespace changes" option when reviewing is recommended.
Some exceptions to this rule:
body
array withoperations
array (direct replacement)body
array withsettings
(direct replacement)